This forum is closed to new posts and
responses. The content has been migrated to the Digital Solutions Community. Please join us there for new content as well as this content. For customer support, please visit the official HCL customer support channels below:
Beg to differ... re: I read all the thread. I feel it's not a bug ~Naomi Deskroterakol 9.Oct.03 07:27 PM a Web browser General 6.0.3; 6.0.2 CF2; 6.0.2 CF1; 6.0.2; 6.0.1 CF3; 6.0.1 CF2; 6.0.1 CF1; 6.0.1; 6.0All Platforms
No matter what the save parameters, if the NotesDocument read into memory on the .GetNextDocument call is anything but the latest version of that document at the time that call is issued, then that's a bug. And its a big bug.
Yes, the particular script here could check for update times, as I've suggested elsewhere, but that's not the point. .GetNextDocument shouldn't return a version of the doc that doesn't include updates since the start of the execution of the current script. It should provide the latest version on disk *INCLUDING TRANSACTIONAL UPDATES*.
Now, in this instance, the developer experiencing the problem should probably just disable transaction logging for this database, since this is available in the advanced options for the database. But in the long-run, this is a pretty serious bug, since it means that a given Lotuscript call can return data that is known to be out of date on a particular server.